Block Placing Tool for Building a User-Defined Algorithm for Electronic Trading

ABSTRACT

Certain embodiments provide a block placing tool for building a user-defined algorithm for electronic trading. Certain embodiments provide for receiving by a block placing tool a selection of one or more blocks. Certain embodiments provide for receiving by a block placing tool a mapping definition including a mapping between block types and/or attributes. Certain embodiments provide for placing blocks based on a selection of blocks and a mapping definition.

BACKGROUND

The presently described technology is directed towards electronic trading systems. More particularly, certain embodiments are directed towards a block placing tool for building a user-defined algorithm for electronic trading.

An electronic trading system generally includes a client device in communication with an electronic exchange that may serve as a host for the client device. Typically, the electronic trading system provides for electronically matching orders to buy and sell tradeable objects to be traded. A tradeable object is an item that may be traded. Stocks, options, futures contracts, securities, and commodities are a few examples of tradeable objects.

The electronic exchange transmits market data to the client device. The market data may include, for example, price data, market depth data, last traded quantity data, data related to a market for the tradeable object, and/or combinations thereof. The client device receives market data from the electronic exchange.

In some electronic trading systems, a client device receives and processes market data without displaying the market data on a display device. For example, a “black-box” algorithmic trading system may run automatically and without displaying market data. However, in other electronic trading systems, the client device displays processed market data on a display device. The client device may include software that creates a trading screen. In general, a trading screen enables a user to participate in an electronic trading session. For example, a trading screen may enable a user to view market data, submit a trade order to the electronic exchange, obtain a market quote, monitor a position, and/or combinations thereof.

In some electronic trading systems, the client device sends trade orders to the electronic exchange. However, in other electronic trading systems, other devices, such as server side devices, are responsible for sending the one or more trade orders to the electronic exchange. Upon receiving a trade order, the electronic exchange enters the trade order into an exchange order book and attempts to match quantity of the trade order with quantity of one or more contra-side trade orders. By way of example, a sell order is contra-side to a buy order with the same price. Similarly, a buy order is contra-side to a sell order with the same price. Unmatched quantity of a trade order is held in the exchange order book until quantity of a trade order is matched by the electronic exchange. Unmatched quantity of a trade order may also be removed from the order book when a trade order is cancelled, either by the client device or electronic exchange. Upon matching quantity of the trade order, the electronic exchange may send a confirmation to the client device that the quantity of the trade order was matched.

Electronic exchanges have made it possible for an increasing number of participants to be active in a market at any given time. The increase in the number of potential market participants has advantageously led to, among other things, a more competitive market and greater liquidity. In a competitive environment, like electronic trading, where every second or a fraction of second counts in intercepting trading opportunities, it is desirable to offer tools that help a participant effectively compete in the marketplace or even give an edge over others.

Some current systems include algorithmic trading systems which may allow for quicker evaluation and reaction to changes in market information. However, such systems typically require skilled programmers to develop the trading algorithms, take days (or even months) to test and debug, and the development and debugging process must be repeated when a trader decides on a different approach or desires a modification to the algorithm's logic.

SUMMARY

The embodiments described herein include, but are not limited to, various devices, systems, methods, and computer program products.

Certain embodiments provide a block placing tool for building a user-defined algorithm for electronic trading. Certain embodiments provide for receiving by a block placing tool a selection of one or more blocks. Certain embodiments provide for receiving by a block placing tool a mapping definition including a mapping between block types and/or attributes. Certain embodiments provide for placing blocks based on a selection of blocks and a mapping definition.

Certain embodiments provide a method including receiving by a computing device a selection of blocks, receiving by the computing device a mapping definition, and placing by the computing device at least one new placed block in an algorithm being designed based on the selection of blocks and the mapping definition. The selection of blocks includes at least one block. Each block in the selection of blocks has a block type. The mapping definition includes at least one mapping. Each mapping in the mapping definition specifies a relationship between a first type and a corresponding second type. The first type includes a first block type. The second type includes a second block type.

Certain embodiments provide a computer readable medium having stored therein instructions executable by a processor, wherein the instructions are executable to receive a selection of blocks, receive a mapping definition, and place at least one new placed block in an algorithm being designed based on the selection of blocks and the mapping definition. The selection of blocks includes at least one block. Each block in the selection of blocks has a block type. The mapping definition includes at least one mapping. Each mapping in the mapping definition specifies a relationship between a first type and a corresponding second type. The first type includes a first block type. The second type includes a second block type.

Other embodiments are described below. In addition, modifications may be made to the described embodiments without departing from the spirit or scope of the inventions.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments are described herein with reference to the following drawings.

FIG. 1 illustrates a block diagram of an electronic trading system in which certain embodiments may be employed.

FIG. 2A illustrates a block diagram of an electronic trading system in which certain embodiments may be employed.

FIG. 2B illustrates a trading interface in which certain embodiments may be employed.

FIGS. 3A-3C illustrate a trading interface according to certain embodiments.

FIGS. 4A-4F illustrate an interface for specifying a mapping definition according to certain embodiments.

FIG. 5 illustrates a flowchart of a method according to certain embodiments.

FIGS. 6A-6B illustrate a trading interface according to certain embodiments.

FIG. 7 illustrates a flowchart of a method according to certain embodiments.

FIG. 8 illustrates a block diagram of a computing device according to certain embodiments.

The foregoing summary, as well as the following detailed description, will be better understood when read in conjunction with the drawings which show certain embodiments. The drawings are for the purpose of illustrating certain embodiments, but it should be understood that the present inventions are not limited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Example Electronic Trading System

FIG. 1 illustrates a block diagram of an electronic trading system 100 in which certain embodiments may be employed. The system 100 includes a client device 110, a gateway 120, and an electronic exchange 130. The client device 110 is in communication with the gateway 120. The gateway 120 is in communication with the exchange 130.

As used herein, the phrase “in communication with” may include in direct communication and indirect communication through one or more intermediary components.

In operation, the client device 110 may send orders to buy or sell tradeable objects at the exchange 130. For example, a user may utilize the client device 110 to send the orders. The orders are sent through the gateway 120 to the exchange 130. In addition, market data is sent from the exchange 130 through the gateway 120 to the client device 110. The user may also utilize the client device 110 to monitor this market data and base a decision to send an order for a tradeable object on the market data.

A tradeable object is anything which can be traded with a quantity and/or a price. For example, financial products such as stocks, options, bonds, futures, currency, warrants, funds derivatives, securities, commodities, traded events, goods, and collections and/or combinations of these may be tradeable objects. A tradeable object may be “real” or “synthetic.” A real tradeable object includes products that are listed by an exchange. A synthetic tradeable object includes products that are defined by the user and are not listed by an exchange. For example, a synthetic tradeable object may include a combination of real (or other synthetic) products such as a synthetic spread created by a trader utilizing a client device 110.

The client device 110 may include one or more electronic computing platforms such as a hand-held device, laptop, desktop computer, workstation with a single or multi-core processor, server with multiple processors, and/or cluster of computers, for example. For example, while logically represented as a single device, client device 110 may include a trading terminal in communication with a server, where collectively the trading terminal and the server are the client device 110. The trading terminal may provide a trading screen to a user and may communicate commands to the server for further processing of the user's inputs through the trading screen, such as placing orders.

The client device 110 is generally owned, operated, controlled, programmed by, configured by, or otherwise used by a user. As used herein, the phrase “user” may include, but is not limited to, a human (for example, a trader) or an electronic trading device (for example, including a processor and memory or an algorithmic trading system). One or more users may be involved in the ownership, operation, control, programming, configuration, or other use, for example.

The client device 110 may include one or more trading applications. The trading application(s) may, for example, process market data by arranging and displaying the market data in trading and charting windows. The market data may be received from exchange 130, for example. As another example, the market data may be received from a simulation environment that provides live or historical data and/or simulates an exchange but does not effectuate real-world trades. This processing may be based on user preferences, for example. The trading application(s) may include an automated trading tool such as an automated spread trading tool, for example. The one or more trading applications may be distributed across one or more of the computing devices of the client device 110. For example, certain components of a trading application may be executed on a trading workstation and other components of the trading application may be executed on a server in communication with the workstation.

The client device 110 may include an electronic trading workstation, a portable trading device, an algorithmic trading system such as a “black box” or “grey box” system, an embedded trading system, and/or an automated trading tool, for example. For example, the client device 110 may be a computing system running a copy of X_TRADER®, an electronic trading platform provided by Trading Technologies International, Inc. of Chicago, Ill. As another example, the client device 110 may be a computing device running an automated trading tool such as Autospreader® and/or Autotrader™, also provided by Trading Technologies International, Inc.

Trading applications may be stored in a computer readable medium of the client device 110. In certain embodiments, certain components of a trading application may be stored on a trading workstation and other components of the trading application may be stored on a server in communication with the workstation. In certain embodiments, one or more components of a trading application may be loaded into the computer readable medium of the client device 110 from another computer readable medium. For example, the trading application (or updates to the trading application) may be stored by a manufacturer, developer, or publisher on one or more CDs or DVDs, which are then provided to someone responsible for loading the application onto the client device 110 or to a server from which the client device 110 retrieves the trading application. As another example, the client device 110 may receive the trading application (or updates to the trading application) from a server, for example, via the Internet or an internal network. The client device 110 may receive the trading application or updates when requested by the client device 110 (“pull distribution”) and/or un-requested by the client device 110 (“push distribution”).

The client device 110 is adapted to send orders to buy or sell a tradeable object. The client device 110 may also be adapted to cancel orders, change orders, and/or query an exchange, for example. As another example, the client device 110 may be adapted to send orders to a simulated exchange in a simulation environment that does not effectuate real-world trades.

The orders sent by the client device 110 may be sent at the request of a user or automatically, for example. For example, a trader may utilize an electronic trading workstation to place an order for a particular tradeable object, manually providing various parameters for the order such as an order price and/or quantity. As another example, an automated trading tool may calculate one or more parameters for an order and automatically send the order. In some instances, an automated trading tool may prepare the order to be sent but not actually send it without confirmation from the user.

In certain embodiments, the client device 110 includes a user interface. The user interface may include one or more display devices for presenting a text-based or graphical interface of a trading application to a user, for example. For example, the display devices may include computer monitors, hand-held device displays, projectors, and/or televisions. The user interface may be used by the user to specify or review parameters for an order using a trading application. The user interface may include one or more input devices for receiving input from a user, for example. For example, the input devices may include a keyboard, trackball, two or three-button mouse, and/or touch screen. The user interface may include other devices for interacting with a user. For example, information may be aurally provided to a user through a speaker and/or received through a microphone.

In certain embodiments, a trading application may include one or more trading screens to enable a trader to interact with one or more markets. Trading screens may enable traders to obtain and view market information, set order entry parameters, enter and cancel orders, and/or monitor positions while implementing various trading strategies, for example. For example, a trading application may receive information (such as bid prices, bid quantities, ask prices, ask quantities, prices and quantities for past sales, and/or other market related information) from exchange 130 which, in turn, may be displayed with a user interface of client device 110. Based on the received information, the trading screen may display a range of price levels and corresponding bid and ask quantities for the price levels in regard to tradeable objects. In order to provide the trader with pertinent trading information, the trading screen may display a range of prices (and the corresponding bid and ask quantities) around the inside market. The information may be continuously or regularly provided to the trading application, which allows the trading application to update the trading screen with current market information. A trader may use the trading screen to place buy and sell orders for tradeable objects or to otherwise trade the tradeable objects based on the displayed information, for example.

Trading screens may include, provide, and/or display one or more trading tools. Trading tools are electronic tools that allow, assist with, and/or facilitate electronic trading. Exemplary trading tools include, but are not be limited to, charts, trading ladders, order entry tools, automated trading tools, automated spreading tools, risk management tools, order parameter tools, order entry systems, market grids, fill windows, market order windows, and enhancements, features, and/or combinations thereof.

In certain embodiments, the client device 110 includes an algorithmic trading application. For example, the client device 110 may include a black box or grey box trading application. As another example, the client device 110 may include a trading application which algorithmically processes market data but provides a user interface to allow a user to manually place orders based on the algorithmic processing or to manipulate orders that were placed automatically. An algorithmic trading application is a trading application which includes an automatically processed algorithm to perform certain actions. That is, the trading application includes an automated series of instructions to perform defined action(s). The actions may include processing market data in a particular way, placing an order, modifying an existing order, deleting an order, refraining from placing an order, selecting which tradeable object(s) to act on, determining a price to place or modify an order at, determining a quantity to place an order at or modify an order to be, determining whether an order should be to buy or sell, and delaying action for a period of time, for example.

As used herein, an algorithm (also referred to as a trading algorithm) is specified by a definition which includes logic expressions and parameters that describe the algorithm to be used in trading. Logic expressions specify the relationship between parameters and may generate more parameters. Parameters may include, for example, inputs into the logic expressions of the algorithm. The definition of an algorithm may be, at least in part, specified by the algorithmic trading application. For example, an algorithmic trading application may allow a user to only specify parameters to be used by pre-defined logic expressions. As another example, an algorithmic trading application may allow a user to specify some or all of the logic expressions and some or all of the parameters. A trading algorithm where the logic expressions are specified by a user is a user-defined trading algorithm.

In certain embodiments, the orders from the client device 110 are sent to the exchange 130 through the gateway 120. The client device 110 may communicate with the gateway 120 using a local area network, a wide area network, a virtual private network, a T1 line, a T3 line, an ISDN line, a point-of-presence, and/or the Internet, for example.

The gateway 120 is adapted to communicate with the client device 110 and the exchange 130. The gateway 120 facilitates communication between the client device 110 and the exchange 130. For example, the gateway 120 may receive orders from the client device 110 and transmit the orders to the exchange 130. As another example, the gateway 120 may receive market data from the exchange 130 and transmit the market data to the client device 110.

In certain embodiments, the gateway 120 performs processing on data communicated between the client device 110 and the exchange 130. For example, the gateway 120 may process an order received from the client device 110 into a data format acceptable by the exchange 130. Similarly, the gateway 120 may transform market data in an exchange-specific format received from the exchange 130 into a format understood by the client device 110. The processing of the gateway 120 may also include tracking orders from the client device 110 and updating the status of the order based on fill confirmations received from the exchange 130, for example. As another example, the gateway 120 may coalesce market data from the exchange 130 and provide it to the client device 120.

In certain embodiments, the gateway 120 provides services other than processing data communicated between the client device 110 and the exchange 130. For example, the gateway 120 may provide risk processing.

The gateway 120 may include one or more electronic computing platforms such as a hand-held device, laptop, desktop computer, workstation with a single or multi-core processor, server with multiple processors, and/or cluster of computers, for example.

The gateway 120 may include one or more gateway applications. The gateway application(s) may, for example, handle order processing and market data processing. This processing may be based on user preferences, for example.

In certain embodiments, the gateway 120 communicates with the exchange 130 using a local area network, a wide area network, a virtual private network, a T1 line, a T3 line, an ISDN line, a point-of-presence, and/or the Internet, for example.

In general, the exchange 130 may be owned, operated, controlled, or used by an exchange entity. Exemplary exchange entities include the CME Group, the London International Financial Futures and Options Exchange (“LIFFE”), the IntercontinentalExchange (“ICE”), and Eurex. The exchange 130 may be an electronic matching system, such as a computer, server, or other computing device, that is adapted to allow tradeable objects, for example, offered for trading by the exchange, to be bought and sold.

The exchange 130 is adapted to match orders to buy and sell tradeable objects. The tradeable objects may be listed for trading by the exchange 130. The orders may include orders received from the client device 110, for example. Orders may be received from the client device 110 through the gateway 120, for example. In addition, the orders may be received from other devices in communication with the exchange 130. That is, typically the exchange 130 will be in communication with a variety of other client devices (which may be similar to client device 110) that also provide orders to be matched.

The exchange 130 is adapted to provide market data. The market data may be provided to the client device 110, for example. The market data may be provided to the client device 110 through the gateway 120, for example. The market data may include data that represents the inside market, for example. The inside market is the lowest sell price (also referred to as the “best ask”) and the highest buy price (also referred to as the “best bid”) at a particular point in time. The market data may also include market depth. Market depth refers to the quantities available at the inside market and may also refer to quantities available at other prices away from the inside market. Thus, the inside market may be considered the first level of market depth. One tick away from the inside market may be considered the second level of market depth, for example. In certain embodiments, market depth is provided for all price levels. In certain embodiments, market depth is provided for less than all price levels. For example, market depth may be provided only for the first five price levels on either side of the inside market. The market data may also include information such as the last traded price (LTP), the last traded quantity (LTQ), and order fill information.

In certain embodiments, the system 100 includes more than one client device 110. For example, multiple client devices similar to the client device 110, discussed above, may be in communication with the gateway 120 to send orders to the exchange 130.

In certain embodiments, the system 100 includes more than one gateway 120. For example, multiple gateways similar to the gateway 120, discussed above, may be in communication with the client device 110 and the exchange 130. Such an arrangement may be used to provide redundancy should one gateway 120 fail, for example.

In certain embodiments, the system 100 includes more than one exchange 130. For example, the gateway 120 may be in communication with multiple exchanges similar to the exchange 130, discussed above. Such an arrangement may allow the client device 110 to trade at more than one exchange through the gateway 120, for example.

In certain embodiments, the system 100 includes more than one exchange 130 and more than one gateway 120. For example, multiple gateways similar to the gateway 120, discussed above, may be in communication with multiple exchanges similar to the exchange 130, discussed above. Each gateway may be in communication with one or more different exchanges, for example. Such an arrangement may allow one or more client devices 110 to trade at more than one exchange (and/or provide redundant connections to multiple exchanges), for example.

In certain embodiments, the client device 110 includes one or more computing devices or processing components. In other words, the functionality of the client device 110 may be performed by more than one computing device. For example, one computing device may generate orders to be sent to the exchange 130 while another computing device may provide a graphical user interface to a trader. In certain embodiments, the gateway 120 includes one or more computing devices or processing components. In other words, the functionality of the gateway 120 may be performed by more than one computing device. In certain embodiments, the exchange 130 includes one or more computing devices or processing components. In other words, the functionality of the exchange 130 may be performed by more than one computing device.

In certain embodiments, the gateway 120 is part of the client device 110. For example, the components of the gateway 120 may be part of the same computing platform as the client device 110. As another example, the functionality of the gateway 120 may be performed by components of the client device 110. In certain embodiments, the gateway 120 is not present. Such an arrangement may occur when the client device 110 does not need to utilize the gateway 120 to communicate with the exchange 130, for example. For example, if the client device 110 has been adapted to communicate directly with the exchange 130.

In certain embodiments, the gateway 120 is physically located at the same site as the client device 110. In certain embodiments, the gateway 120 is physically located at the same site as the exchange 130. In certain embodiments, the client device 110 is physically located at the same site as the exchange 130. In certain embodiments, the gateway 120 is physically located at a site separate from both the client device 110 and the exchange 130.

While not shown for the sake of clarity, in certain embodiments, the system 100 may include other devices that are specific to the communications architecture such as middleware, firewalls, hubs, switches, routers, exchange-specific communication equipment, modems, security managers, and/or encryption/decryption devices.

The components, elements, and/or functionality of the system 100 discussed above may be implemented alone or in combination in various forms in hardware, firmware, and/or as a set of instructions in software, for example. Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, CD-ROM, DVD, EPROM, and/or file server, for execution on a general purpose computer, one or more computing devices, or other processing device.

II. Algo Design Lab

FIG. 2A illustrates a block diagram of an electronic trading system 200 in which certain embodiments may be employed. The system 200 includes one or more client devices 201, one or more algorithm servers 202, and one or more electronic exchanges 203. Each client device 201 is in communication one or more algorithm servers 202. Each algorithm server 202 is in communication with one or more exchanges 203. In addition, in certain embodiments, although not shown in FIG. 2A, a client device 201 may also be in communication with one or more exchanges 203. Communication with an exchange by a client device 201 and/or an algorithm server 202 may be done through a gateway similar to the gateway 120, discussed above, for example.

Client device 201 may be similar to client device 110, discussed above, for example. In certain embodiments, the client device 201 may be referred to as a trader terminal. Exchange 203 may be similar to exchange 130, discussed above, for example.

In certain embodiments, the algorithm server 202 is located physically near or at an exchange 203. In certain embodiments, the algorithm server 202 is part of the client device 201.

In operation, an algorithm for electronic trading may be designed on a client device 201. The algorithm may then be communicated to an algorithm server 202. The algorithm server 202 executes the algorithm to perform electronic trading with the exchange 203. Market data may be received by the algorithm server 202 for use by the algorithm. In addition, market data may be received by the client device 201 for use in designing the algorithm. The market data may be received from the exchange 203, for example. As another example, market data may be received from a simulator or from stored/historical data.

FIG. 2B illustrates a trading interface 210 in which certain embodiments may be employed. The trading interface 210 is a trading interface for an algorithmic trading application referred to as the Algo Design Lab (“ADL”). The ADL allows a trader to design an algorithm for electronic trading. Aspects of the ADL are discussed in U.S. patent application Ser. No. 12/905,709, entitled “User-Defined Algorithm Electronic Trading”, filed Oct. 15, 2010, which is herein incorporated by reference in its entirety. It is understood that certain embodiments may be incorporated into trading interfaces other than the ADL.

The trading interface 210 includes a design canvas area 211, a block list area 212, a variable area 213, and a control area 214. In certain embodiments one or more of these areas may be in separate windows or toolbars. For example, the block list area 212 may be in a separate window from the design canvas area 211.

In operation, an algorithm is defined in the design canvas area 211 by utilizing one or more blocks from the block list area 212. Default values for user-defined variables in the algorithm may be specified using the variable area 213. Once the algorithm has been defined, the algorithm may be simulated using controls in the control area 214 to indicate how the logic of the algorithm will behave. An order to be managed according to the defined algorithm may then be initiated using a trading interface.

The design canvas area 211 provides for defining an algorithm. The design canvas area 211 may also be referred to as a whiteboard area. The design canvas area 211 provides a visual programming environment for designing the algorithm. Designing an algorithm includes building, testing, simulating, and/or evaluating the algorithm.

In certain embodiments, the design canvas area 211 is the primary focus of the interface for the trading application 210 and may be a large, white space, for example. In the design canvas area 211, blocks may be arranged according to the preference of the user. In certain embodiments, the design canvas area 211 provides grid lines that may be used to arrange the blocks. In certain embodiments, the design canvas area 211 includes an overview display or map that may be used to navigate through a large algorithm with many blocks. In certain embodiments, the design canvas area 211 may be zoomed in or out so that a user may see more or less of the algorithm at a time.

Blocks are placed in the design canvas area 211 and connected to define the algorithm. The blocks to be placed may be selected from the block list area 212. Once a block has been placed, it may then be connected to other placed blocks.

The block list area 212 includes one or more blocks which may be selected and placed in the design canvas area 211. Blocks represent different functionalities that may be combined according to user preference to build an algorithm.

In general, blocks have inputs and outputs. However, certain blocks may have only inputs and others may have only outputs. For example, a pause block may have only an input. As another example, a number block may have only an output.

Inputs and outputs of blocks are of one of two primary types: continuous or discrete. A continuous type input/output, at any particular point in time (hence continuous) has a value. A discrete type input/output receives/provides discrete events (individual messages/objects) corresponding to specific actions/events that occur at some particular point in time. When a specific action/event occurs, a corresponding discrete event may be generated.

In addition to the primary type of the input/output, an input/output may have a particular value types. For example, a continuous input might have a value type of Boolean, number, integer, floating point number, or instrument. As another example, a block may have two continuous inputs of a variable value type, where the value type for the two inputs may be Boolean or numeric, for example, but must match. An equals block, which takes two inputs and compares them to output a Boolean indicating whether the inputs are equal may have variable inputs so that it may be used to compare Booleans or numbers or instruments, for example. As another example, a discrete output might have a value type of fill confirmation. That is, the discrete output might provide fill confirmation discrete events. As another example, a discrete output might provide more than one type of discrete event for actions such as order request confirmations (indicating an order was placed), fill confirmations (indicating an order was filled or partially filled), order change confirmations (indicating a working order parameters such as price or quantity was changed), order deletion confirmations (indicating a working order was deleted or cancelled), or trade confirmations (indicating a trade has occurred). As another example, a discrete event may be empty in that it indicates only that an event has occurred. An empty discrete event may, for example, be triggered by a timer, a change in a Boolean value, or used to activate a portion of an algorithm at a particular time (such as a time of day or a time when certain market conditions have been met, for example). A discrete event of a particular type may include different information than a discrete event of another type. For example, an order confirmation may include information such as an order identifier and/or an instrument. As another example, a fill confirmation discrete event may include information such as an order identifier, price, quantity, instrument, and/or time of a fill. As another example, an order deletion confirmation may include an order identifier, instrument, and/or time of deletion. As another example, an empty discrete event may not include any information (or may include only a time the event occurred). A discrete event may include user-defined information. For example, a discrete event a fill confirmation for a filled order for instrument A may include user-defined market information such as a bid price in instrument B at the time of the fill in instrument A.

In certain embodiments, a block includes indicators of the primary type for its inputs/outputs. For example, continuous inputs/outputs may be indicated with a particular background color, foreground color, background pattern, border color, border style, shape, symbol, number, text, and/or font and discrete inputs/outputs might be indicated with another color, pattern, border, shape, symbol, number, text, and/or font.

In certain embodiments, a block includes indicators of the value type for its inputs/outputs. For example, inputs/outputs with a particular value type may be indicated with a particular background color, foreground color, background pattern, border color, border style, shape, symbol, number, text, and/or font and inputs/outputs with a different value type may be indicated with another color, pattern, border, shape, symbol, number, text, and/or font.

In certain embodiments, the primary type and/or the value type of an input or output is displayed in a pop-up window when a cursor is positioned near the block. In certain embodiments, information about the configuration of a block is displayed in a pop-up window when a cursor is positioned near the block.

Blocks represent different functionality. In the trading interface 210, blocks have been separated into four general categories of functionality: basic blocks, trading blocks, discrete blocks, and miscellaneous blocks. However, these groupings are for convenient organization and utilization by a user; blocks do not need to be grouped and a block's group does not necessitate particular features. Some blocks may appropriately fit in more than one category and other organizations or groupings of blocks may also be employed.

Basic blocks generally have continuous inputs and outputs and provide arithmetic operations (for example, addition, subtraction, multiplication, and division), logical operations (for example, AND, OR, and comparison such as equality, greater than, and less than), constant values (for example, number and Boolean), and if-then-else constructs. Basic blocks may include add, subtract, multiply, divide, greater than, less than, greater than or equal, less than or equal, AND, OR, equals, IF-THEN-ELSE, number, Boolean, and constant blocks, for example.

Trading blocks generally provide more complex functionality related to manipulating an order (for example, placing an order, modifying an existing order, or deleting an order) or order-related information (for example, a fill confirmation). Trading blocks may have both continuous and discrete inputs and outputs. For example, a market maker block may have continuous inputs for specifying an instrument, price, quantity, and condition for quoting an order and may have a continuous output of the working quantity and a discrete output for providing notification of fills. Trading blocks allow users, including non-programmers (such as traders), to utilize a visual design environment (such as that provided by the ADL) to create and deploy trading algorithms. The trading blocks may allow for more rapid and accurate design of an algorithm as compared to a typical programmer with fewer steps or instructions as compared to other visual programming platforms. Trading blocks may include instrument, instrument attribute, market maker, legger, custom spread, responsive buy/sell, conditional buy/sell, order handler, IF-THEN-ELSE instrument, instrument attribute at price, spread between, trade, order, fill calculator, and fill accumulator blocks, for example.

Discrete blocks generally have discrete inputs and outputs and provide operations based on the occurrence of discrete events. For example, a generator block may generate an occurrence of a discrete event. As another example, a value extractor block may extract a value from a discrete event and make it available as a continuous value to another portion of the algorithm. As another example, a sequencer block may be used to control the sequence in which subsequent blocks are processed in response to a discrete event. Certain discrete blocks may store data to be referenced at a subsequent time. For example, a value accumulator block may receive a discrete event and extract a user-specified value from it. The extracted value may be accumulated with values extracted from each received discrete event. Discrete blocks may include generator, value extractor, value accumulator, value bucket, discrete moving average, state, branch, multiplexer, funnel, sequencer, discrete min, and discrete max blocks, for example.

Miscellaneous blocks provide a variety of functionality that may not necessary fit into the above-discussed categories. For example, these blocks may provide special purpose or more complex calculations or may add additional control to the execution of the algorithm itself. Further, miscellaneous blocks may provide more precise tools to control risk, convert numbers into tradeable values, or use time (either precise or elapsed) as an input or variable. Miscellaneous blocks may include min, max, rounding, display to decimal, not, once true, is number, moving average, conditional f(x), numeric f(x), average, timer, note, random number, square root, log, and pause blocks, for example.

III. Block Placing Tool for Building a User-Defined Algorithm

Certain embodiments provide a block placing tool for building a user-defined algorithm for electronic trading. Certain embodiments provide for receiving by a block placing tool a selection of one or more blocks. Certain embodiments provide for receiving by a block placing tool a mapping definition including a mapping between block types and/or attributes. Certain embodiments provide for placing blocks based on a selection of blocks and a mapping definition.

FIGS. 3A-3C illustrate a trading interface 300 according to certain embodiments. The trading interface 300 includes a design canvas area 310 and a plurality of placed blocks 321-327. The trading interface 300 may be similar to the trading interface 210, discussed above, for example. The design canvas area 310 may be similar to the design canvas area 211, discussed above, for example.

As illustrated in FIG. 3A, a definition for a trading algorithm is being designed using the trading interface 300. The illustrated example trading algorithm is a scalping algorithm that will, when certain conditions are met, buy at the best bid price and then attempt to sell at one trading increment above the fill price, typically making a profit of one trading increment per unit bought and sold. Other trading algorithms may be designed using the trading interface 300.

More particularly, the algorithm includes a buy market maker block 321 and a sell market maker block 326. The buy market maker block 321 is a market maker block configured to work buy orders. The buy market maker block 321 is provided with an instrument to buy (“ESZ0”) specified by an instrument block. The buy market maker block 321 is provided with a price to buy at specified by an instrument field block 322 which provides the best bid price (“124550”) for the instrument. Note that the prices and quantities shown are for a particular instant in time since the market for the instrument may be changing over time. The buy market maker block 321 is provided with a fixed quantity of 5 to buy specified by a number block. The condition input of the buy market maker block 321 is provided a Boolean value determined based on several other blocks (“the condition logic”). The condition logic compares the best bid quantity (provided by the instrument block 323) (“108”) for the instrument to determine if it is greater than the best ask quantity (provided by the instrument block 324) (“16”). This result (“TRUE”) is then ANDed with a comparison of the best bid quantity (provided by the instrument block 325) (“619”) of another instrument (“ESH1”) to determine if it is greater than fixed quantity of 250 specified by a number block. The AND block provides the Boolean value for the condition logic (“TRUE”) to the condition input of the buy market maker block 321. When the condition input is TRUE, the buy market maker block 321 will work a buy order and when the condition is FALSE, the buy market maker block 321 will remove/refrain from working the buy order. When the buy market maker block 321 receives fill confirmations for the buy order it is working, a discrete event is generated.

The sell market maker block 326 is a market maker block configured to work sell orders. The sell market maker block 326 is part of the covering logic 330. The covering logic 330 will work sell orders to cover positions taken by the buy market maker block 321. The sell market maker block 326 is provided with the same instrument (“ESZ0”) to sell. The sell market maker block 326 is provided with a price to sell at specified by an adder block 327 which adds the minimum price increment for the instrument (provided by an instrument field block) (“25”) to the fill price (provided by a value extractor block from the discrete event generated by the buy market maker block 321 when a fill confirmation is received). The sell market maker block 326 is provided with a quantity to sell specified by an accumulator block which provides the accumulated quantity that has been bought by the buy market maker block 321, which is extracted from the discrete events generated when fill confirmations are received by the buy market maker block 321.

Thus, when the algorithm is run, the buy market maker block 321 will, when the condition logic indicates to do so, attempt to buy a quantity of 5 at the best bid price (perhaps across multiple buy orders) and sell (perhaps across multiple sell orders) a quantity to match the filled buy quantity at the fill price plus the minimum price increment.

As illustrated in FIG. 3B, the covering logic 330 of the scalping algorithm illustrated in FIG. 3A has been grouped in virtualized group block 340. An instance of a virtualized group block is created for each discrete event that is provided to the virtualized group block. That is, each time a discrete event is received at virtualized group block 340, a new instance of the virtualized group block 340 is created to handle the discrete event. This allows each discrete event be handled by the covering logic 330 based on the information particular to the fill discrete event provided by the buy market marketer block 321.

While the behavior of the scalping algorithm illustrated in FIG. 3B may by preferred by a trader, for clarity the following discussion will address the scalping algorithm as illustrated in FIG. 3A. It should be understood, however, that the block placing tool discussed herein may operate with group blocks, nested group blocks, and/or virtualized blocks.

As discussed above, the algorithm illustrated in FIG. 3A places buy order(s) and, when those buy order(s) are filled, sell order(s) are place to cover them. However, it may be desirable to a trader to have the algorithm include similar logic that, concurrently with the existing logic, places sell order(s) and, when those sell order(s) are filled, buy order(s) are placed to cover them.

A block placing tool is a tool of a trading interface that may be used to place new blocks in the algorithm being designed. The block placing tool places blocks based on a selection of blocks and a mapping of block types and/or attributes.

The block placing tool may be activated through an action such as selecting a menu item or pressing one more keys. For example, an “Import & Reverse” men item may be selected to activate the block placing tool. As another example, a “reverse” option may be selected from a pop-up menu for a selected block to activate the block placing tool. As another example, a key combination such as “Control-R” may be pressed to activate the block placing tool. In certain embodiments, the block placing tool may be accessed using a copy-and-paste-style operation. For example, a “Paste Special” interface may be provided to activate the block placing tool.

The selection of blocks may be determined in a variety of ways. For example, the selected blocks may be determined to be all of the placed blocks. As another example, the selected blocks may be determined to be the placed blocks visible in the design canvas area when the block placing tool is activated. As another example, the selected blocks may be determined based on a user selection. As another example, the selected blocks may be determined based on a defined subset of blocks. All blocks of certain selected and/or pre-defined types may be determined to be the selected blocks, for example. As another example, the selected blocks may be determined to be the blocks in a stored module or library. As another example, the selected blocks may be determined to be one or more blocks on a toolbar. In certain embodiments, one or more of these example techniques for determining the selected blocks are employed.

As illustrated in FIG. 3C, the blocks of the scalping algorithm have been selected by a user using a cursor to draw a box 350 around them. Other user interface techniques may also be used by the user to select the blocks. For example, a user may click using a user input device controlling a cursor in combination with the shift or control key being pressed, for example. The selected blocks may also be determined using other techniques, discussed above, for example.

In certain embodiments, the selection of blocks is determined prior to the activation of the block placing tool. For example, a user may use a cursor to select placed blocks to be used by the block placing tool and then activate the block placing tool with a menu selection. In certain embodiments, the selection of blocks is determined during the activation of the block placing tool. For example, a user may activate the block placing tool with a key combination and the block placing tool may determine the selected blocks to be the blocks visible when activated. In certain embodiments, the selection of blocks is determined after the activation of the block placing tool. For example, the block placing tool may be activated and then lead a user through a series of steps to complete the placement including selecting the blocks to be used by the tool.

A mapping of block types and/or attributes specifies a relationship between a one block type and a second block type. The second block type corresponds to the first block type in the mapping. The first block may be referred to as the source block, the input block, or the original block, for example. The second block may be referred to as the destination block or the output block, for example.

In general, a mapping may be between two related or complementary block types and/or attributes (such as “Adder Block” to “Subtract Block” or an Instrument Field block with a “Best Bid Price” attribute to a “Best Ask Price” attribute). However, such a relationship is not required. A mapping may be between blocks that share common input and output types for inputs and outputs that are connected. For example, an Instrument Field block which includes an attribute specifying the instrument (such as “ESZ0”) as well as the particular value (such as “Best Bid Price”) may have no inputs and a single numeric output. Such a block may be mapped to a constant number block, which also may have no inputs and a single numeric output, for example.

In certain embodiments, the block type specified in the mapping definition includes an attribute of the block. For example, a mapping definition may include a block type (such as an “Instrument Field” block) which may have one or more particular attributes specified (such as “Bid Price” or “Bid Quantity”). In this case, the particular attribute configured for a block may be viewed as an extension of the block type (such as “Instrument Field—Bid Price”). That is, when referring to the “type” of a block, this may include both the block's actual type and an attribute, for example. There may be one or more “levels” of attributes (such as “Instrument Field—Bid Price—USD”, which may be an Instrument Field block that provides the best bid price in U.S. dollars) that may provide levels of specificity with respect to the block type, for example. In certain embodiments, the mapping may include entries for both the first block type and an optional entry for an attribute of the first block. Similarly, the mapping may include entries for the second block type and an attribute of the second block.

The mapping of block types and/or attributes may be defined in a variety of ways. For example, the mapping definition may be user-specified. As another example, the mapping definition may be determined each time the block placing tool is activated. As another example, the mapping definition may be pre-defined based on a user preference. As another example, the mapping definition may be pre-defined by a trading application. As another example, the mapping definition may be hard coded. As another example, the mapping definition may be determined based on the selection of blocks. As another example, the mapping definition may be determined heuristically by the trading interface based on the selection of blocks, visible blocks, and/or blocks being used in the algorithm. In certain embodiments, one or more of these example techniques for determining the mapping definition are employed.

In certain embodiments, the mapping definition is determined prior to the activation of the block placing tool. For example, a trading application may include pre-defined mappings (either hard coded or that a user may modify) that have been configured before the user activates the block placing tool with a menu selection and that are used for each activation of the block placing tool. In certain embodiments, the mapping definition is determined during the activation of the block placing tool. For example, a user may activate the block placing tool with a key combination and the block placing tool may determine the mapping definition heuristically based on the blocks visible when activated. In certain embodiments, the mapping definition is determined after the activation of the block placing tool. For example, the block placing tool may be activated and then lead a user through a series of steps to complete the placement including determining the mapping definition to be used by the tool. As another example, the block placing tool may be activated by initiating a “Paste Special” command as part of a copy-and-paste-style operation in the trading interface and an interface for determining the mapping definition may then be provided prior to the block placing tool placing the new blocks.

FIGS. 4A-4F illustrate an interface 400 for specifying a mapping definition according to certain embodiments.

As illustrated in FIG. 4A, the interface 400 includes a block type interface 410, a source mapping interface 420, a destination mapping interface 430, an add button 440, and a block mapping region 450.

In operation, the interface 400 allows a user to specify a mapping definition for use with a block placement tool. A block type is selected from the block type interface 410. Depending on the particular block type selected, the source mapping interface 420 and/or the destination mapping interface 430 may be enabled to specify the mapping of block types and/or attributes. Once the source and/or destination mappings have been specified (if needed), the specified mapping may be added to the mapping definition. The block mapping region 450 displays the mappings included in the mapping definition.

As illustrated in FIG. 4B, the block type interface 410 indicates that the “MarketMakerBlock” block type has been selected. The source mapping interface 420 and the destination mapping interface 430 have been grayed out because the mapping for a market maker block is pre-defined to be flipping (or replacing) a buy market maker block to a sell market maker block and a sell market maker block to a buy market maker block.

As illustrated in FIG. 4C, when the add button 440 is pressed subsequent to the selection discussed above in reference to FIG. 4B, the mapping is added to the mapping definition and shown in the block mapping region 450 as mapping 451.

As illustrated in FIG. 4D, the block type interface 410 indicates that the “Instrument Field” block type has been selected. The source mapping interface 420 and the destination mapping interface 430 are activated to allow selection of the source and destination attributes for the instrument field block to be specified in the mapping definition. As illustrated, the source mapping has been selected to be the “Bid Price” attribute and the destination mapping is being selected as the “Ask Price” attribute. Thus, the mapping to be added to the mapping definition is that an instrument field block with an attribute of “Bid Price” will be mapped to an instrument field block with an attribute of “Ask Price.”

As illustrated FIG. 4E, the block type interface 410 indicates that the “AdderBlock” block type has been selected. The source mapping interface 420 is grayed out because it is not needed for this block type. The destination mapping interface 430 is activated to allow selection of the destination block type to be specified in the mapping definition. As illustrated, the destination mapping is being selected to be the “SubtractBlock” block type. Thus, the mapping to be added to the mapping definition is that an “AdderBlock” will be mapped to a “SubtractBlock.”

As illustrated in FIG. 4F, the block mapping region 450 shows each of the mappings specified for the mapping definition. More particularly, the mapping definition includes mappings 451-455. As discussed above, mapping 451 represents a mapping for a market maker block where the buy/sell setting of a market maker block is flipped to be sell/buy. Mapping 452 represents a mapping for an instrument field block with a “Bid Price” attribute being mapped to an instrument field block with an “Ask Price” attribute. Mapping 453 represents a mapping for an instrument field block with a “Bid Quantity” attribute being mapped to an instrument field block with an “Ask Quantity” attribute. Mapping 454 represents a mapping for an instrument field block with an “Ask Quantity” attribute being mapped to an instrument field block with a “Bid Quantity” attribute. Mapping 455 represents a mapping of an “AdderBlock” to a “SubtractBlock.”

Once the block placing tool has been activated and the selection of the blocks and the mapping definition have each been determined, the block placing tool may place new blocks in the algorithm based on the selection of blocks and the mapping definition.

In certain embodiments, the new blocks placed by the block placing tool are placed into a new group block. For example, a user may select an option for the block placing tool to place the new blocks into a new group block in the algorithm.

In certain embodiments, the block placing tool determines the new blocks and, rather than placing the new blocks in the algorithm, performs another action. For example, the block placing tool may create a new module or library containing the determined new blocks. As another example, the block placing tool may put the determined new blocks into a clipboard so that a user may place the determined new blocks into the algorithm through a “paste” operation.

FIG. 5 illustrates a flowchart 500 of a method according to certain embodiments. Some or all of the method illustrated in the flowchart 500 may be performed by a block placing tool to place new blocks, for example. The method is described with reference to elements of systems discussed above, but it should be understood that other implementations are possible. The flowchart 500 for the method begins at block 510.

At block 510, a selected block is selected from the selection of blocks. The selection of blocks is the selection of blocks determined as discussed above. In general, the selected block may be a block in the selection of blocks that has not previously been selected as the selected block. For example, the selected block may be determined using an iterator that traverses the blocks in the selection of blocks. As discussed above, the selection of blocks may include blocks such as group blocks, nested group blocks, and/or virtualized blocks. In such a case, the method may recurse through the group blocks or otherwise iterate through them, for example. The method then proceeds to block 520.

At block 520, the selected block is evaluated to determine if the type of the selected block is specified in the mapping definition. The selected block is the block selected in block 510, discussed above. The mapping definition is the mapping definition determined as discussed above.

Determining if the type of the selected block is specified in the mapping definition may includes evaluating, where appropriate, if an attribute of the selected block is specified in the mapping definition. For example, a mapping definition may include a block type (such as an “Instrument Field” block) which may have one or more particular attributes specified (such as “Bid Price” or “Bid Quantity”). In this case, the particular attribute configured for a block may be viewed as an extension of the block type (such as “Instrument Field—Bid Price”) for the purpose of determining if the type of the selected block is specified in the mapping definition.

In certain embodiments, the evaluation of the attribute may be made as a separate evaluation. In the embodiment illustrated in FIG. 5, the evaluation of the type of the selected block includes both the type of the selected block and, where appropriate, its attributes.

If the type of the selected block is not specified in the mapping definition, the method proceeds to block 530. For example, assuming the mapping definition is similar to the mapping definition shown in FIG. 4F, if the selected block is a “GreaterThanBlock” (which is not in the mapping definition), then it is desirable that the block placing tool place a new “GreaterThanBlock” into the algorithm. If the type of the selected block is specified in the mapping definition, the method proceeds to block 540. For example, assuming the mapping definition is similar to the mapping definition shown in FIG. 4F, if the selected block is an “AdderBlock” (which is specified in mapping 455), then it is desirable that the block placing tool place a new “SubtractBlock” into the algorithm.

At block 530, the type of the new block is determined to be the same as the type of the selected block. The method then proceeds to block 550.

At block 540, the type of the new block is determined to be the mapped block type specified in the mapping definition. The method then proceeds to block 550.

At block 550, the new block is placed. The type of then new block is the type determined in block 530 or block 540, as appropriate. Once the new block is placed, the method proceeds to block 510 to select another block or ends if no other block should be selected. For example, the method may end if each block in the selected blocks has been traversed.

One or more of the blocks of the flow chart 500 discussed above may be implemented alone or in combination in various forms in hardware, firmware, and/or as a set of instructions in software, for example. Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, CD-ROM, DVD, EPROM, and/or file server, for execution on a general purpose computer, one or more computing devices, or other processing device.

Certain embodiments may omit one or more of these blocks and/or perform the blocks in a different order than the order listed. For example, some blocks may not be performed in certain embodiments. As a further example, certain blocks may be performed in a different temporal order, including simultaneously, than listed above.

FIGS. 6A-6B illustrate a trading interface 300 according to certain embodiments. As illustrated in FIG. 6A, the trading interface 300 is shown after a block placing tool has be used. The originally placed blocks 611 are the blocks shown in FIG. 3A and are unaltered by the block placing tool. The newly placed blocks 612 are the blocks placed by the block placing tool based on the blocks selected as illustrated in FIG. 3C according to the mapping definition illustrated in FIG. 4F.

As illustrated in FIG. 6B, trading interface 300 has been zoomed to show only the newly placed blocks 612. The buy market maker block 321 and the sell market maker block 326 have been mapped to the sell market maker block 621 and the buy market maker block 626, respectively, according to mapping 451. The instrument field block 322 with the “Bid Price” attribute has been mapped to the instrument field block 622 with the “Ask Price” attribute, according to mapping 452. The instrument field block 323 and the instrument field block 325, each with the “Bid Quantity” attribute, have been mapped to the instrument field block 623 and the instrument field block 626, respectively, each with the “Ask Quantity” attribute, according to mapping 453. The instrument field block 324 with the “Ask Quantity” attribute has been mapped to the instrument field block 624 with the “Bid Quantity” attribute, according to mapping 454. The adder block 327 has been mapped to the subtract block 627, according to mapping 455. For the other blocks in the selection of blocks illustrated in FIG. 3C, these blocks were not specified in the mapping definition and thus the block placing tool just placed copies of those blocks.

The components, elements, and/or functionality of the interfaces 300 and 400 discussed above may be implemented alone or in combination in various forms in hardware, firmware, and/or as a set of instructions in software, for example. Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, CD-ROM, DVD, EPROM, and/or file server, for execution on a general purpose computer, one or more computing devices, or other processing device.

FIG. 7 illustrates a flowchart 700 of a method according to certain embodiments. Some or all of the method illustrated in the flowchart 700 may be performed by a block placing tool, for example. The method is described with reference to elements of systems discussed above, but it should be understood that other implementations are possible. The flowchart 700 for the method begins at block 710.

At block 710, a selection of blocks is determined. The selection of blocks may be determined as discussed above, for example. In certain embodiments, the selection of blocks is determined by a user. In certain embodiments, the selection of blocks is determined by a block placing tool. The method then proceeds to block 720.

At block 720, the selection of blocks is received. The received selection of blocks may be, or may be based on, the selection of blocks determined at block 710 discussed above, for example. The method then proceeds to block 730.

At block 730, a mapping definition is determined. The mapping definition may be determined as discussed above, for example. In certain embodiments, the mapping definition is determined by a user. In certain embodiments, the mapping definition is determined by a block placing tool. The method then proceeds to block 740.

At block 740, the mapping definition is received. The received mapping definition may be, or may be based on, the mapping definition determined at block 730 discussed above, for example. The method then proceeds to block 750.

At block 750, the new blocks are placed based on the selection of blocks and the mapping definition. The selection of blocks may be the selection of blocks received at block 720 discussed above, for example. The mapping definition may be the mapping definition received at block 740 discussed above, for example. One or more new blocks may be placed by a block placing tool as discussed above, for example. In certain embodiments, a block placing tool uses the method illustrated by the flowchart 500 in FIG. 5, discussed above.

One or more of the blocks of the flow chart 700 discussed above may be implemented alone or in combination in various forms in hardware, firmware, and/or as a set of instructions in software, for example. Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, CD-ROM, DVD, EPROM, and/or file server, for execution on a general purpose computer, one or more computing devices, or other processing device.

Certain embodiments may omit one or more of these blocks and/or perform the blocks in a different order than the order listed. For example, some blocks may not be performed in certain embodiments. As a further example, certain blocks may be performed in a different temporal order, including simultaneously, than listed above.

IV. Example Computing Device

FIG. 8 illustrates a block diagram of a computing device 800 according to certain embodiments. The client device 110 may include one or more computing devices 800, for example. The client device 201 may include one or more computing devices 800, for example. The algorithm server 202 may include one or more computing devices 800, for example. The gateway 120 may include one or more computing devices 800, for example. The exchange 130 may include one or more computing devices 800, for example. The exchange 203 may include one or more computing devices 800, for example.

The computing device 800 includes a bus 810, a processor 820, a memory 830, a network interface 840, a display device 850, an input device 860, and an output device 870. The computing device 800 may include additional, different, or fewer components. For example, multiple buses, multiple processors, multiple memory devices, multiple network interfaces, multiple display devices, multiple input devices, multiple output devices, or any combination thereof, may be provided. As another example, the computing device 800 may not include an output device 870 separate from the display device 850. As another example, the computing device 800 may not include a display device 850. As another example, the computing device 800 may not include an input device 860. Instead, for example, the computing device 800 may be controlled by an external or remote input device via the network interface 840.

The bus 810 may include a communication bus, channel, network, circuit, switch, fabric, or other mechanism for communicating data between components in the computing device 800. The bus 810 may be communicatively coupled with and transfer data between any of the components of the computing device 800. For example, during an installation process of a trading application, one or more computer-readable instructions that are to be executed by the processor 820 may be transferred from an input device 860 and/or the network interface 840 to the memory 830. When the computing device 800 is running or preparing to run the trading application stored in the memory 830, the processor 820 may retrieve the instructions from the memory 830 via the bus 810.

The processor 820 may include a general processor, digital signal processor, application specific integrated circuit, field programmable gate array, analog circuit, digital circuit, programmed processor, combinations thereof, or other now known or later developed processing device. The processor 820 may be a single device or a combination of devices, such as associated with a network or distributed processing. Any processing strategy may be used, such as multi-processing, multi-tasking, parallel processing, and/or remote processing, for example. Processing may be local or remote and may be moved from one processor to another processor.

The processor 820 may be operable to execute logic encoded in one or more tangible media, such as memory 830 and/or via network device 840. As used herein, logic encoded in one or more tangible media includes instructions that are executable by the processor 820 or a different processor. The logic may be stored as part of software, hardware, integrated circuits, firmware, and/or micro-code, for example. The logic may be received from an external communication device via a communication network, for example, connected to the Internet. The processor 820 may execute the logic to perform the functions, acts, or tasks illustrated in the figures or described herein.

The memory 830 may be tangible media, such as computer readable storage media, for example. Computer readable storage media may include various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media, any combination thereof, or any other now known or later developed tangible data storage device. The memory 830 may include a single device or multiple devices. For example, the memory 830 may include random access memory and hard drive storage. The memory 830 may be adjacent to, part of, programmed with, networked with, and/or remote from processor 820, such that data stored in the memory 830 may be retrieved and processed by the processor 820, for example.

The memory 830 may store instructions that are executable by the processor 820. The instructions may be executed to perform one or more of the acts or functions described herein or shown in the figures.

The network interface 840 may be a one-way or two-way communication coupling. Accordingly, the network interface 840 may communicatively connect one, two, or more communication networks or devices. For example, the bus 810 may be coupled with a gateway similar to gateway 120 discussed above via the network interface 840, such that one, some, or all of the components of the computing device 800 are accessible or can communicate with the gateway. As another example, the network interface 840 may couple the bus 810 with other communication networks. The network interface 840 may be, for example, an integrated services digital network (ISDN) card or a modem to provide a data communication connection. As another example, network interface 840 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN, for example, connected to the Internet. Wireless links may also be implemented. The network interface 840 may send and receive electrical, electromagnetic, or optical signals that carry analog or digital data streams representing various type of information, for example.

The display device 850 may include a visual output device, cathode ray tube (CRT) display, electronic display, electronic paper, flat panel display, light-emitting diode (LED) displays, electroluminescent display (ELD), plasma display panels (PDP), liquid crystal display (LCD), thin-film transistor displays (TFT), organic light-emitting diode displays (OLED), surface-conduction electron-emitter display (SED), laser television, carbon nanotubes, nanocrystal displays, head-mounted display, projector, three-dimensional display, transparent display device, and/or other now known or later developed display, for example.

The display device 850 is adapted to display a trading screen. The trading screen may be similar to the trading screens discussed above, for example. The trading screen may be interactive. An interactive trading screen may allow, for example, one or more trading actions to be performed using the trading screen. For example, an interactive trading screen may allow one or more order entry parameters to be set and/or sent using one or more order entry actions. The display device 850 and/or input device 860 may be used to interact with the trading screen, for example.

The input device 860 may include a keyboard, mouse, microphone, touch-screen, trackball, keypad, joystick, and/or other device for providing input, for example. The input device 860 may be used, for example, to provide command selections to processor 820. For example, the input device 860 may be a mouse that is used to control a cursor displayed on a trading screen. The mouse may include one or more buttons for selection and control, for example.

The output device 870 may include a keyboard, mouse, speakers, touch-screen, trackball, keypad, haptic device or system, joystick, and/or other device for providing output, for example. For example, the output device 870 may be used to output one or more signals, such as a haptic signal or an audio signal, to a user.

While the present inventions have been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the inventions. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the inventions without departing from their scope. Therefore, it is intended that the inventions not be limited to the particular embodiments disclosed, but that the inventions will include all embodiments falling within the scope of the claims. 

1. A method including: receiving by a computing device a selection of blocks, wherein the selection of blocks includes at least one block, wherein each block in the selection of blocks has a block type; receiving by the computing device a mapping definition, wherein the mapping definition includes at least one mapping, wherein each mapping in the mapping definition specifies a relationship between a first type and a corresponding second type, wherein the first type includes a first block type, wherein the second type includes a second block type; and placing by the computing device at least one new placed block in an algorithm being designed based on the selection of blocks and the mapping definition.
 2. The method of claim 1, wherein the selection of blocks includes all blocks placed in the algorithm prior to placing the at least one new placed block.
 3. The method of claim 1, wherein the selection of blocks is determined by a user.
 4. The method of claim 1, wherein the selection of blocks is determined automatically by the computing device.
 5. The method of claim 1, wherein the mapping definition is pre-defined.
 6. The method of claim 1, wherein the mapping definition is determined by a user.
 7. The method of claim 1, wherein the mapping definition is determined automatically by the computing device.
 8. The method of claim 1, wherein the first type includes a first attribute and the second type includes a second attribute for at least one mapping in the mapping definition.
 9. The method of claim 1, wherein the mapping definition is received before the selection of blocks is received.
 10. The method of claim 1, wherein the selection of blocks and the mapping definition are received when a block placing tool is activated.
 11. The method of claim 1, wherein placing the at least one new placed block includes: selecting by the computing device a selected block from the selection of blocks; determining by the computing device whether the block type of the selected block conforms to a mapping in the mapping definition; determining by the computing device a new block type, wherein the new block type is the corresponding block type specified in the mapping when the block type of the selected block conforms to the mapping and the new block type is the block type of the selected block when the block type of the selected block does not conform to a mapping in the mapping definition; and placing by the computing device a new block of the determined new block type.
 12. A computer readable medium having stored therein instructions executable by a processor, wherein the instructions are executable to: receive a selection of blocks, wherein the selection of blocks includes at least one block, wherein each block in the selection of blocks has a block type; receive a mapping definition, wherein the mapping definition includes at least one mapping, wherein each mapping in the mapping definition specifies a relationship between a first type and a corresponding second type, wherein the first type includes a first block type, wherein the second type includes a second block type; and place at least one new placed block in an algorithm being designed based on the selection of blocks and the mapping definition.
 13. The computer readable medium of claim 12, wherein the selection of blocks includes all blocks placed in the algorithm prior to placing the at least one new placed block.
 14. The computer readable medium of claim 12, wherein the selection of blocks is determined by a user.
 15. The computer readable medium of claim 12, wherein the selection of blocks is determined automatically.
 16. The computer readable medium of claim 12, wherein the mapping definition is pre-defined.
 17. The computer readable medium of claim 12, wherein the mapping definition is determined by a user.
 18. The computer readable medium of claim 12, wherein the mapping definition is determined automatically.
 19. The computer readable medium of claim 12, wherein the first type includes a first attribute and the second type includes a second attribute for at least one mapping in the mapping definition.
 20. The computer readable medium of claim 12, wherein the mapping definition is received before the selection of blocks is received.
 21. The computer readable medium of claim 12, wherein the selection of blocks and the mapping definition are received when a block placing tool is activated.
 22. The computer readable medium of claim 12, wherein the instructions to place the at least one new placed block further include instructions executable to: select a selected block from the selection of blocks; determine whether the block type of the selected block conforms to a mapping in the mapping definition; determine a new block type, wherein the new block type is the corresponding block type specified in the mapping when the block type of the selected block conforms to the mapping and the new block type is the block type of the selected block when the block type of the selected block does not conform to a mapping in the mapping definition; and place a new block of the determined new block type. 